Improve AM62X U-Boot documentation#711
Conversation
The previous build structure, split by R5/A53 followed by device, meant your eyes had to jump around to find the instructions for the one device you were compiling. Instead, a better way would be to first split by device, so that users can follow one contiguous set of instructions, since they need to build both R5 and A53. Signed-off-by: Yiyoung Liu <y-liu20@ti.com>
BeaglePlay has custom defconfigs (am62x_beagleplay_a53_defconfig and am62x_beagleplay_r5_defconfig) just like other community boards already documented (e.g. BeagleBadge), so it should be included in the build guide. Signed-off-by: Yiyoung Liu <y-liu20@ti.com>
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds clearer navigation and board-specific build guidance for K3 U-Boot documentation.
Changes:
- Added an introductory description and internal navigation links to the K3 target images page.
- Added BeaglePlay defconfig entries to the build matrix.
- Restructured K3 build instructions into per-board rubrics with explicit R5/A53 command blocks and clarified output artifacts/dependencies.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| source/linux/Foundational_Components/U-Boot/BG-Target-Images-K3.rst | Adds intro context and quick links to key sections. |
| source/linux/Foundational_Components/U-Boot/BG-Build-K3.rst | Adds BeaglePlay configs and reorganizes build instructions into clearer board-specific blocks. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Since the first subsection is build/boot related, while the second subsection is technical information relating to binary layouts, a user may be confused if the first subsection is necessary for them to read at all (it is!) if no clarification is provided. Signed-off-by: Yiyoung Liu <y-liu20@ti.com>
cdfc43a to
ecc5e6e
Compare
|
@jmenti , @sathish-8 please review. |
| A53 | ||
| $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" am62x_beagleplay_a53_defconfig O=$UBOOT_DIR/out/a53 | ||
| $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" CC="$CC_64" BL31=$TFA_DIR/build/k3/lite/release/bl31.bin TEE=$OPTEE_DIR/out/arm-plat-k3/core/tee-pager_v2.bin O=$UBOOT_DIR/out/a53 BINMAN_INDIRS=$TI_LINUX_FW_DIR | ||
|
|
There was a problem hiding this comment.
So does this mean we are now going to include build instructions for a beagle devices? I thought we had agreed this was not a good idea... @StaticRocket @praneethbajjuri and beagle device should have their own documentation in /Supported Boards??? For ex. BeagleBadge: https://software-dl.ti.com/processor-sdk-linux/esd/AM62LX/12_00_00_07_04/exports/docs/boards/index.html
There was a problem hiding this comment.
Ah, yeah. Need to capture that summary somewhere.
Improved U-Boot documentation structure:
Reorganized the AM62X build instructions to group by device first (AM62X, AM62X LP, AM62SIP), then architecture (R5 A53). Added documentation for BeaglePlay support with its custom defconfigs.
Additionally, improved the Target Images documentation by adding an introductory paragraph that reiterates the practical "copy to SD card" section and clarifies that Image Formats is reference material.